home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
fdhm210.arc
/
FDHMNODE.DOC
< prev
next >
Wrap
Text File
|
1991-09-27
|
5KB
|
142 lines
FDHMNODE Vers. 1.01
Copyright (c) 1991 by Ulrich Bartelt
FidoNetnode 2:241/5800
FDHMNode is a special nodelistcompiler to use with the
following programs:
FDHM 2.10 - the FrontDoor History-Manager
TrackM 4.30 - the best netmail utility in the world
RA 2.?? - the best BBS in the world
NODEInfo - a stand allone program to use with FDHMNode
FDHMNode is fully compatible with RANODE.EXE that comes with
the Remote-Access BBS. That means the output is the same.
Unfortunately not everyone is running all of the above software
products. RANODE requires a RA-environment. FDHMNode does not!
The advantage of FDHMNode (and RANODE) is the **VERY** small
index file that gives full access to the raw-nodelist.
The disadvantage is that you have your raw-nodelist up-to-date
every time you run one of the above programs.
FDHM and TrackM 4.30 will stop working if they detect that anything
is wrong with your nodelists files.
The great thing using a special nodelist index with FDHM is that
you have fully access to all information in the nodelist and you
have to setup only a very few things to make things running. Your
setup is up-to-date now and forever 'cause it gets its information
from the nodelists and if something changed in the nodelist its
automatically updated in FDHM.
┌──────────────┐
│ Installation │
└──────────────┘
NONE ! If you run FrontDoor, FDHMNode should get everything it needs
from your FD environment.
┌───────────────┐
│ Configuration │
└───────────────┘
Without any other information FDHMNode will compile the latest
nodelist and places its index files in the nodelist directory.
That's enough if you only run one nodelist and want to use
NodeInfo.
To work with FDHM you have to set-up a small controlfile to define
the costs and/or additional nodelists to include in the index.
Use the following keywords:
PVTLIST <nodelist> ( up to 10 lists )
Nodelist has to be a fully qualified name with extension
or you may use .??? for the extension. In the last case
FDHMNode will automatically search for the latest file.
NOTE: Do *NOT* define NODELIST here, 'cause FDHMNode
will ever take the normal nodelist without any
setup.
We are not in DOS, you have to say .??? not .* !!
DEFAULT <timezone> [ or costs ]
Default timezone to use in FDHM. Normally the zone for
oversea calls
ZONE <zone> <timezone> [or costs] ( max. 50 )
Normally a lower value than DEFAULT for your own zone.
REGION <region> <timezone> [or costs] ( max. 50 )
Setup for special regions that does not match with a
zone statement. Normally a lower value for your own
region.
Please see the file FDHMNODE.CTL that comes with this program!
┌──────────────┐
│ Requirements │
└──────────────┘
FDHMNode will compile all and everything. But in order to work
correct your nodelist files must have at least one zone statement.
So if you want to compile a private pointlist, make sure a
zone is on top of the list.
╔══════════╗
║ NODEINFO ║
╚══════════╝
NodeInfo is a special program that makes use of the index files
from FDHMNode. Feel free to rename it to a shorter name like NI
if you don't start the 'Norton-Integrator' then ;-)
You may use NodeInfo on the commandline with an optional address
or just say NODEINFO and it will prompt you for one.
NodeInfo knows about your own address, so you can give addresses
in the short form. Examples:
I am 2:241/5800
0 will list 2:241/0
4444 will list 2:241/4444
512/1 will list 2:512/1
One special treatment is made to list your points: If you have
set the POINTNET variable you may enter
.4 to list zone:pointnet/4